Description:

Allow the ability to deprecate specific configuration keys with optional replacements and optional invalidation dates to make less breaking changes. Here's how it works:

• cv.deprecated now takes additional parameters replacement_key, invalidation_version, default
• If all of those are provided, it checks if this version of Home Assistant has crossed the invalidation_version and if not raises a warning indicating what the replacement key to use is.
• It will then grab the value from the deprecated parameter and insert it into replacement parameter, replacing the original.
• If it has crossed the invalidation_version it raises vol.Invalid with the same message indicating how to resolve the problem.

I've demonstrated with the update_interval configuration key being replaced with the scan_interval configuration key in the freedns component.

This needs a few more tests before this can be merged. A good next step would be to surface this in the UI.

Related issue (if applicable): Spawned from discussion in #20526.

Checklist:

• The code change is tested and works locally.
• Local tests pass with tox. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.

If the code does not interact with devices:

• Tests have been added to verify that the new code works.